Initial checkin of the monorepo structure + sw-appcache-behavior #1
Conversation
| import path from 'path'; | ||
| import promisify from 'promisify-node'; | ||
|
|
||
| export let globPromise = promisify('glob'); |
There was a problem hiding this comment.
Given that this is a style thing, and we have time constraints, I wouldn't block this but I'm opening a separate issue to discuss naming conventions. #2
|
I have ignored the stuff in If that's a correct assumption then LGTM. |
| @@ -0,0 +1,9 @@ | |||
| { | |||
|
Merging, and will put together some follow-up PRs to resolve repo issues not addressed in this PR. |
|
Hi, I am not familiar with how service workers work, I have an application that uses appcache. Is this the right tool to convert my current application to use service workers instead? Is there any how-to site or document or am I just expected to drill through your code and also to learn everything about service workers before I can get started? Very new to this side of things. |
|
@mattiaswelander please raise questions here: https://github.com/GoogleChrome/sw-appcache-behavior |
R: @addyosmani @gauntface @wibblymat
CC: @jakearchibald @jpmedley
Here's a (very large—sorry!) code dump of where I currently stand with the monorepo infrastructure + the first project,
sw-appcache-behavior. There are some things that are still a work-in-progress, but it's far enough along to start breaking up additions into follow-up PRs.Monorepo Implementation Status
npmpublishing.sw-appcache-behavior Status
The
sw-appcache-behaviorcode was reviewed in jeffposnick/appcache2serviceworker#1